On Demand Customization of Mobile Computing Devices

ABSTRACT

Embodiments of the invention describe mobile computing device configuration processes. A device executing configuration logic may wirelessly transmit power to a mobile computing device housed within a sealed product packaging to charge a battery power supply of the mobile computing device. A short-range wireless communication link is established with the mobile computing device housed within the sealed product packaging to install a firmware image on the mobile computing device, wherein the firmware image is to be selected based, at least in part, on a geographic location of the mobile computing device. The short-range wireless communication link is then used to activate a wireless network interface of the mobile computing device housed within the sealed product packaging to connect to a boot server including an OS image for the mobile computing device to download and install.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. patent application Ser. No.14/229,565 filed on Mar. 28, 2014, the entire disclosure of which ishereby incorporated by reference.

FIELD

Embodiments of the present invention generally pertain to computingdevices and more specifically to mobile computing devices.

BACKGROUND

Computing devices, such as mobile computing devices, may be configuredto execute different applications or operating systems; thus, eventhough devices may have the same underlying hardware, their respectiveapplications and/or operating systems need to be customized andinstalled prior to their shipment. Furthermore, language specific usersoftware and interfaces for computing devices are installed prior totheir shipment. The challenge of this process is that a devicemanufacturer needs to estimate how many devices with certain softwareconfigurations are needed at the production phase. If these estimatesare inaccurate, they may create a shortage or a surplus of devices withcertain configurations.

BRIEF DESCRIPTION OF THE DRAWINGS

The following description includes discussion of figures havingillustrations given by way of example of implementations of embodimentsof the invention. The drawings should be understood by way of example,and not by way of limitation. As used herein, references to one or more“embodiments” are to be understood as describing a particular feature,structure, or characteristic included in at least one implementation ofthe invention. Thus, phrases such as “in one embodiment” or “in analternate embodiment” appearing herein describe various embodiments andimplementations of the invention, and do not necessarily all refer tothe same embodiment. However, they are also not necessarily mutuallyexclusive.

FIG. 1 is a flow diagram of a process for configuring a mobile computingdevice according to an embodiment of the invention.

FIG. 2A and FIG. 2B are illustrations of a mobile computing deviceincluded in a sealed product packaging to be configured according to anembodiment of the invention.

FIG. 3 is an illustration of a mobile computing device configuration anddistribution process according to an embodiment of the invention.

FIG. 4 is an illustration of a mobile computing device configurationoperation according to an embodiment of the invention.

FIG. 5 is a block diagram of computing components to execute mobilecomputing device configuration processes to an embodiment of theinvention.

FIG. 6 illustrates a mobile computing device communicatively coupled toa remote device according to an embodiment of the invention.

Descriptions of certain details and implementations follow, including adescription of the figures, which may depict some or all of theembodiments described below, as well as a discussion of other potentialembodiments or implementations of the inventive concepts presentedherein. An overview of embodiments of the invention is provided below,followed by a more detailed description with reference to the drawings.

DETAILED DESCRIPTION

Embodiments of the invention describe apparatuses, systems and methodsfor on demand customization of mobile computing devices. Throughout thisspecification, several terms of art are used. These terms are to take ontheir ordinary meaning in the art from which they come, unlessspecifically defined herein or the context of their use would clearlysuggest otherwise. In the following description numerous specificdetails are set forth to provide a thorough understanding of theembodiments. One skilled in the relevant art will recognize, however,that the techniques described herein can be practiced without one ormore of the specific details, or with other methods, components,materials, etc. In other instances, well-known structures, materials, oroperations are not shown or described in detail to avoid obscuringcertain aspects.

FIG. 1 is a flow diagram of a process for configuring a mobile computingdevice according to an embodiment of the invention. Flow diagrams asillustrated herein provide examples of sequences of various processactions. Although shown in a particular sequence or order, unlessotherwise specified, the order of the actions can be modified. Thus, theillustrated implementations should be understood only as examples, andthe illustrated processes can be performed in a different order, andsome actions may be performed in parallel. Additionally, one or moreactions can be omitted in various embodiments of the disclosure; thus,not all actions are required in every implementation. Other processflows are possible.

Process 100 is shown to include operations to wireless charge a batterysupply of a mobile computing device housed in a sealed product packaging(i.e., retail packaging), 102. Wirelessly charging the battery of themobile computing device enables the device to be activated withoutcoupling a power cable to the device, thereby enabling the device toremain in its sealed product packaging. Said battery of the mobilecomputing device may be wirelessly charged by any known means (e.g.,inductively charged via a generated electromagnetic field from anexternal power supply, as illustrated and described below).

Once the battery supply is sufficiently charged, a short range wirelesscommunication link is established initiating an update mode for themobile computing device, 104. This short range wireless communicationlink may comprise a Near Field Communication (NFC) link, a Bluetoothlink, or any equivalent short range wireless communication link fortransferring data. In one embodiment, said update mode is executed forinstalling a firmware image on the mobile computing device, 104. Saidfirmware image is utilized for activating the mobile computing device,and for configuring a subsequent operating system (OS) installation orupdate. For mobile computing devices comprising cellular connectivity,said firmware may also include operations specific to a cellular serviceprovider.

A wireless network connection is configured for the mobile computingdevice and a boot-up device, which is used to install software images,106, such as an OS image. Said OS image may be stored on a boot-updevice such as a boot server. The appropriate OS vendor and language forthe OS image may be identified by the previously downloaded firmwareimage, or may be identified by a user interface of a softwareinstallation package.

Software images are installed and/or updated on the mobile computingdevice via the wireless network link, 108. For example, a complete OSimage may downloaded and installed on the mobile computing device. Insome embodiments, OS update patches are installed so that the mobilecomputing device has the most up-to-date version of the OS. Applicationsto be executed via the OS may also be installed.

Thus, in embodiments of the invention, mobile computing devices may beshipped from the manufacturer with minimal (if any) software installed,so that the devices may be customized at the distribution level, theretail level, etc.; in other words, instead of packaging different typesdevices, wherein the devices differ in software/firmware only,customization is done after the device is shipped. Embodiments of theinvention therefore allow for the optimization of factory, logistics anddevice inventory storage operations.

Another benefit of customizing mobile computing devices after themanufacture phase is that it is possible to customize the mobilecomputing device for the eventual user. In this embodiment, user datafrom a second mobile computing device is copied to the packaged mobilecomputing device, 110. Thus, at a retail location for example, it ispossible to transfer data and settings from a user's current device to anew device sealed in its retail packaging.

FIG. 2A and FIG. 2B are illustrations of a mobile computing deviceincluded in a sealed product packaging to be configured according to anembodiment of the invention. In this embodiment, mobile computing device200 is illustrated as being included in sealed product packaging 210(the illustration of device 200 of FIG. 2A is a cutaway view, as thedevice is enclosed in the sealed product packaging). Mobile computingdevice 200 is shown to comprise a smartphone, but in other embodiments,said mobile computing device may comprise any mobile device, such as alaptop computer, tablet computing device, wearable computing device,etc.

Mobile computing device 200, housed in packaging 210, is placed onwireless charging mat 220 to charge a battery power supply of the mobilecomputing device. When mobile computing device 200 is placed inpackaging 210, it is in a power off state; wirelessly charging thebattery power supply of the mobile computing device makes it possible tostart the device without utilizing a physical connection, therebyenabling packaging 210 to remain sealed.

While any known wireless charging means may be used, FIG. 2B illustratesthat wireless charging mat 220 includes coil 222 to generate a magneticfield for transmitting power. Coil 212 is shown to be included inpackaging 210 to be charged inductively from the magnetic fieldgenerated by coil 222 of wireless charging mat 220. The placement ofcoil 212 within packaging 210 may vary, as long it is placed towards theexpected location of the corresponding charging coil (i.e., in thisembodiment, coil 222). In some embodiments, coil 212 is included inmobile computing device 200 (e.g., the coil may comprise a printedcircuit board (PCB) coil). In other embodiments, coil 212 is included ahousing separate from mobile computing device 200, and is electricallycoupled to the battery power supply of the device. Characteristics ofcoils 212 and 222, such as wire size, wire material, size and shape ofthe coils, etc., may vary in other embodiments.

FIG. 3 is an illustration of a mobile computing device configuration anddistribution process according to an embodiment of the invention. Inthis embodiment, plurality of devices 300 are shown to be shipped fromthe manufacturer to one or more distributors. As described above, eachof devices 300 are shipped from the manufacturer in a sealed packagingwith minimal software installed.

At the distribution level, devices (such as device 301) are wirelesslycharged and individually loaded with software; this software is selectedbased on several factors—e.g., destination region, retailer, intendedservice provider, etc. As described above, short range wireless link311, e.g., an NFC link, is used to securely identify a startup mode fordevice initialization. NFC communication may be used by configurationlogic 314 to transmit data connection details to device 301, e.g. theidentify of Wi-Fi access point (AP) 310 and its security information.Said logic may comprise, for example, a general purpose processorexecuting application code, hardware circuitry integrated into a systemon a chip, a dedicated system processor running firmware, an ASIC, etc.

Device 301 then connects to one or more network services that includesoftware builds 312—i.e., different OS and software variants. While onedevice is shown in this example, other embodiments may install OS andapplication software for several devices at once. For example, in oneembodiment, different Wi-Fi networks are utilized for different OSvariants.

In this example, a plurality of OS variants are installed on subsets ofplurality of devices 300. Subsets 320 and 322 are shown to includedifferent OS variants. Thus, plurality of devices 300 are shipped fromthe manufacture comprising the same underlying hardware and minimalinstalled software. Each of these devices is customized at thedistribution level, without opening their respective sealed productpackaging to allow for the optimization of factory, logistics and deviceinventory storage operations.

FIG. 4 is an illustration of a mobile computing device configurationoperation according to an embodiment of the invention. In thisembodiment, device 400, included in sealed product packaging 402, isshown to utilize Wi-Fi AP 420 for receiving user data from user device410. This user data may include, for example, device and applicationconfigurations (e.g., user Wi-Fi AP settings, user email accounts, userapplication login data, device home screen settings, etc.) and user data(e.g., photos, videos, web browsing data, etc.). Thus, device 400 iscustomized according to the user (i.e., user device 420) at the point ofpurchase (i.e., the retail location for the device) without havingsealed product packaging 402 opened.

FIG. 5 is a block diagram of computing components to execute mobilecomputing device configuration processes to an embodiment of theinvention. Device 500 may comprise either a mobile computing deviceincluded in a sealed product packaging as described above, or maycomprise a device including mobile computing device configuration logicto execute the configuration processes described above. It will beunderstood that certain of the components are shown generally, and notall components of such a device are shown in device 500. Furthermore, itwill be understood that any of the illustrated components may bediscrete components or may be components included on a system on a chip(SoC) integrated circuit (IC), and may be communicatively coupledthrough any direct or indirect means.

Device 500 includes one or more processor cores 510, which performs theprimary processing operations of device 500. Each of processor core(s)510 can be SoC components, or can be included in one or more physicaldevices, such as single or multi-core microprocessors, applicationprocessors, microcontrollers, programmable logic devices, or otherprocessing means. The processing operations performed by processorcore(s) 510 include the execution of an operating platform or operatingsystem on which applications and/or device functions are executed. Theprocessing operations include operations related to I/O (input/output)with a human user or with other devices, operations related to powermanagement, and/or operations related to connecting device 500 toanother device. The processing operations may also include operationsrelated to audio I/O and/or display I/O.

In one embodiment, device 500 includes audio subsystem 520, whichrepresents hardware (e.g., audio hardware and audio circuits) andsoftware (e.g., drivers, codecs) components associated with providingaudio functions to the computing device. Audio functions can includespeaker and/or headphone output, as well as microphone input via any ofthe audio jacks described above. Devices for such functions can beintegrated into device 500, or connected to device 500. In oneembodiment, a user interacts with device 500 by providing audio commandsthat are received and processed by processor core(s) 510.

I/O controller 540 represents hardware devices and software componentsrelated to interaction with a user. I/O controller 540 can operate tomanage hardware that is part of audio subsystem 520 and/or displaysubsystem 530. Additionally, I/O controller 540 illustrates a connectionpoint for additional devices that connect to device 500 through which auser might interact with the system. For example, devices that can beattached to device 500 might include microphone devices, speaker orstereo systems, video systems or other display device, keyboard orkeypad devices, or other I/O devices for use with specific applicationssuch as card readers or other devices.

As mentioned above, I/O controller 540 can interact with audio subsystem520 and/or display subsystem 530. For example, input through amicrophone or other audio device can provide input or commands for oneor more applications or functions of device 500. Additionally, audiooutput can be provided instead of or in addition to display output.Display subsystem 530 includes a touchscreen, and thus the displaydevice also acts as an input device, which can be at least partiallymanaged by I/O controller 540. There can also be additional buttons orswitches on device 500 to provide I/O functions managed by I/Ocontroller 540. Sensor subsystem 590 may comprise any touch sensor(e.g., touch sensors in addition to the touchscreen of display subsystem530) and/or motion detectors.

In one embodiment, I/O controller 540 manages devices such asaccelerometers, cameras, light sensors or other environmental sensors,or other hardware that can be included in device 500. The input can bepart of direct user interaction, as well as providing environmentalinput to the system to influence its operations (such as filtering fornoise, adjusting displays for brightness detection, applying a flash fora camera, or other features). In one embodiment, device 500 includespower management 550 that manages battery power usage, charging of thebattery, and features related to power saving operation.

Memory subsystem 560 includes memory devices for storing information indevice 500. Memory can include nonvolatile (state does not change ifpower to the memory device is interrupted) and/or volatile (state isindeterminate if power to the memory device is interrupted) memorydevices. Memory 560 can store application data, user data, music,photos, documents, or other data, as well as system data (whetherlong-term or temporary) related to the execution of the applications andfunctions of system 500. Memory 560 further stores firmware imagesrelated to boot path operations, and thus may include DRAM devices tostore said firmware images as described above.

Connectivity 570 includes hardware devices (e.g., wireless and/or wiredconnectors and communication hardware) and software components (e.g.,drivers, protocol stacks) to enable device 500 to communicate withexternal devices. The device could be separate devices, such as othercomputing devices, wireless access points or base stations, as well asperipherals such as headsets, printers, or other devices.

Connectivity 570 can include multiple different types of connectivity.To generalize, device 500 is illustrated with cellular connectivity 572and wireless connectivity 574. Cellular connectivity 572 refersgenerally to cellular network connectivity provided by wirelesscarriers, such as provided via GSM (global system for mobilecommunications) or variations or derivatives, CDMA (code divisionmultiple access) or variations or derivatives, TDM (time divisionmultiplexing) or variations or derivatives, or other cellular servicestandards (e.g., UMTS, EV-DO, WiMAX, or LTE). Wireless connectivity 574refers to wireless connectivity that is not cellular, and can includeNFC communication links, personal area networks (such as Bluetooth),local area networks (such as Wi-Fi), and/or wide area networks (such asWi-Max), or other wireless communication.

Peripheral connections 580 include hardware interfaces and connectorsfor implementing non-flash firmware storage support as described above,as well as software components (e.g., drivers, protocol stacks) to makeperipheral connections. It will be understood that device 500 could bothbe a peripheral device (“to” 582) to other computing devices, as well ashave peripheral devices (“from” 584) connected to it.

Device 500 may have a “docking” connector to connect to other computingdevices for purposes such as managing (e.g., downloading and/oruploading, changing, synchronizing) content on device 500. Additionally,a docking connector can allow device 500 to connect to certainperipherals that allow device 500 to control content output, forexample, to audiovisual or other systems. In addition to a proprietarydocking connector or other proprietary connection hardware, device 500can make peripheral connections 580 via common or standards-basedconnectors. Common types can include a Universal Serial Bus (USB)connector (which can include any of a number of different hardwareinterfaces), DisplayPort including MiniDisplayPort (MDP), HighDefinition Multimedia Interface (HDMI), Firewire, or other type.

FIG. 6 illustrates a mobile computing device communicatively coupled toa remote device according to an embodiment of the invention. System 600includes mobile computing device 610 and remote device 620communicatively coupled via communication link 650. Link 650 maycomprise a short range wireless connection or wireless networkconnection.

Mobile computing device 610 may comprise any of the described orinferred embodiments discussed above, such as a laptop computer, asmartphone, a tablet computing device, or a wearable computing device.Remote device 620 may exchange data with device 610 via link 650.

Remote device 620 may comprise any type of computing device ortransmitter suitable for executing the mobile computing deviceconfiguration operations discussed above including a laptop computer, adesktop computer, a server, etc. Remote device 620 and device 610 mayeach contain hardware to enable communication link 650, such asprocessors, transmitters, receivers, antennas, etc.

Various components referred to above as processes, servers, or toolsdescribed herein may be a means for performing the functions described.Each component described herein includes software or hardware, or acombination of these. Each and all components may be implemented aslogic such as software modules, hardware modules, special-purposehardware (e.g., application specific hardware, ASICs, DSPs, etc.),embedded controllers, hardwired circuitry, hardware logic (e.g., ageneral purpose processor executing application code, hardware circuitryintegrated into an SoC, a dedicated system processor running firmware,an ASIC, etc.), etc. Software content (e.g., data, instructions,configuration) may be provided via an article of manufacture including anon-transitory, tangible computer or machine readable storage medium,which provides content that represents instructions that can beexecuted. The content may result in a computer performing variousfunctions/operations described herein.

A computer readable non-transitory storage medium includes any mechanismthat provides (i.e., stores and/or transmits) information in a formaccessible by a computer (e.g., computing device, electronic system,etc.), such as recordable/non-recordable media (e.g., read only memory(ROM), random access memory (RAM), magnetic disk storage media, opticalstorage media, flash memory devices, etc.). The content may be directlyexecutable (“object” or “executable” form), source code, or differencecode (“delta” or “patch” code). A computer readable non-transitorystorage medium may also include a storage or database from which contentcan be downloaded. Said computer readable medium may also include adevice or product having content stored thereon at a time of sale ordelivery. Thus, delivering a device with stored content, or offeringcontent for download over a communication medium may be understood asproviding an article of manufacture with such content described herein.

Embodiments of the invention describe apparatuses comprising logic, atleast partially implemented in hardware (e.g., a general purposeprocessor executing application code, hardware circuitry integrated intoan SoC, dedicated system processor running firmware, an ASIC, etc.).Said logic is to wirelessly transmit power to a mobile computing devicehoused within a sealed product packaging to charge a battery powersupply of the mobile computing device, establish a short-range wirelesscommunication link with the mobile computing device housed within thesealed product packaging to install a firmware image on the mobilecomputing device, wherein the firmware image is to be selected based, atleast in part, on a geographic location of the mobile computing device,and use the short-range wireless communication link to activate awireless network interface of the mobile computing device housed withinthe sealed product packaging to connect to a boot server including anoperating system (OS) image for the mobile computing device to downloadand install.

In some embodiments, this logic is to further copy user data from asecond mobile computing device to the mobile computing device housedwithin the sealed product packaging via the wireless network link. Insome embodiments, the logic is to further select one of a plurality ofOS images based, at least in part, on the geographic location of themobile computing device. In some of these embodiments, the OS image isselected based on a language related to the geographic location of themobile computing device, and/or is selected based on a vendor identityassociated with the geographic location of the mobile computing device.

In some embodiments, the logic is to connect to a server including an OSupdate patch for the mobile computing device to download and install. Insome embodiments, the short-range wireless communication link comprisesa Near Field Communication (NFC) link and/or a Bluetooth communicationlink. In some embodiments, the mobile computing device comprises atleast one of a smartphone, a tablet computing device, or a wearablecomputing device.

Embodiments of the invention describe a system including a processor, amemory, a wireless charging transmitter to wirelessly transmit power toa mobile computing device housed within a sealed product packaging tocharge a battery power supply of the mobile computing device, ashort-range wireless communication interface to establish a short-rangewireless communication link with the mobile computing device housedwithin the sealed product packaging, and mobile computing deviceconfiguration logic. This logic is to install a firmware image on themobile computing device, the firmware image stored in the memory, anduse the short-range wireless communication link to activate a wirelessnetwork interface of the mobile computing device housed within thesealed product packaging to connect to a boot server including anoperating system (OS) image for the mobile computing device to downloadand install.

In some embodiments, the mobile computing device configuration logic isto further configure the mobile computing device to copy user data froma second mobile computing device via the wireless network link. In someembodiments, the mobile computing device configuration logic is tofurther select one of a plurality of OS images based, at least in part,on a geographic location of the mobile computing device. In some ofthese embodiments, the OS image is selected based on a language relatedto the geographic location of the mobile computing device, and/or isselected based on a vendor identity associated with the geographiclocation of the mobile computing device.

In some embodiments, the mobile computing device configuration logic isto further configure the mobile computing device to connect to a serverincluding an OS update patch for the mobile computing device to downloadand install. In some embodiments, the short-range wireless communicationinterface comprises a Near Field Communication (NFC) interface and/or aBluetooth communication interface. In some embodiments, the mobilecomputing device to comprise at least one of a smartphone, a tabletcomputing device, or a wearable computing device.

Embodiments of the invention describe a least one computer readablestorage medium having instructions stored thereon that, when executed onat least one machine, cause the machine(s) to wirelessly transmit powerto a mobile computing device housed within a sealed product packaging tocharge a battery power supply of the mobile computing device, establisha short-range wireless communication link with the mobile computingdevice housed within the sealed product packaging to install a firmwareimage on the mobile computing device, wherein the firmware image is tobe selected based, at least in part, on a geographic location of themobile computing device, and use the short-range wireless communicationlink to activate a wireless network interface of the mobile computingdevice housed within the sealed product packaging to connect to a bootserver including an operating system (OS) image for the mobile computingdevice to download and install.

In some embodiments, the machine(s) is to further copy user data from asecond mobile computing device to the mobile computing device housedwithin the sealed product packaging via the wireless network link. Insome embodiments, the machine(s) is to further select one of a pluralityof OS images based, at least in part, on the geographic location of themobile computing device. In some of these embodiments, the OS image isselected based on a language related to the geographic location of themobile computing device, and/or is selected based on a vendor identityassociated with the geographic location of the mobile computing device.In some embodiments, the machine(s) is to further connect to a serverincluding an OS update patch for the mobile computing device to downloadand install.

1. An apparatus, comprising: logic, at least partially implemented inhardware, to: wirelessly transmit power to a mobile computing devicehoused within a sealed product packaging to charge a battery powersupply of the mobile computing device; establish a short-range wirelesscommunication link with the mobile computing device housed within thesealed product packaging to install a firmware image on the mobilecomputing device; use the short-range wireless communication link toactivate a wireless network interface of the mobile computing devicehoused within the sealed product packaging to connect to a boot serverincluding an operating system (OS) image for the mobile computing deviceto download and install; and configure the mobile computing device tolink the mobile computing device within the sealed product packagingwith a second mobile computing device using the wireless network, themobile computing device to obtain user data and user configurations fromthe second mobile computing device via the wireless network link tocustomize the mobile computing device according to user preferences. 2.The apparatus claim 1, wherein the logic is to further: select one of aplurality of OS images for the mobile computing device.
 3. The apparatusof claim 2, wherein the OS image is selected based on a language for themobile computing device.
 4. The apparatus of claim 2, wherein the OSimage is selected based on a vendor identity for the mobile computingdevice.
 5. The apparatus of claim 1, wherein the logic is to further:connect to a server including an OS update patch for the mobilecomputing device to download and install.
 6. The apparatus of claim 1,wherein the short-range wireless communication link comprises a NearField Communication (NFC) link.
 7. The apparatus of claim 1, wherein theshort-range wireless communication link comprises a Bluetoothcommunication link.
 8. The apparatus of claim 1, wherein the mobilecomputing device comprises at least one of a smartphone, a tabletcomputing device, or a wearable computing device.
 9. The apparatus claim1, wherein the user configurations include one or more of the followingfor the second mobile computing device: Wi-Fi settings; user emailaccount settings; user application login data; and device home screensettings.
 10. The apparatus of claim 1, wherein the user data includesone or more of the following from the second mobile computing device:photo data; video data; and web browsing data.
 11. A system comprising:a processor; a memory; a wireless charging transmitter to wirelesslytransmit power to a mobile computing device housed within a sealedproduct packaging to charge a battery power supply of the mobilecomputing device; a short-range wireless communication interface toestablish a short-range wireless communication link with the mobilecomputing device housed within the sealed product packaging; and mobilecomputing device configuration logic to: install a firmware image on themobile computing device; use the short-range wireless communication linkto activate a wireless network interface of the mobile computing devicehoused within the sealed product packaging to connect to a boot serverincluding an operating system (OS) image for the mobile computing deviceto download and install, and configure the mobile computing device tolink the mobile computing device within the sealed product packagingwith a second mobile computing device using the wireless network, themobile computing device to obtain user data and user configurations fromthe second mobile computing device via the wireless network link tocustomize the mobile computing device according to user preferences. 12.The system of claim 11, wherein the firmware image to be installed is tobe stored in the memory of the system.
 13. The system of claim 11, themobile computing device configuration logic to further: select one of aplurality of OS images for the mobile computing device.
 14. The systemof claim 13, wherein the OS image is selected based on a language forthe mobile computing device.
 15. The system of claim 13, wherein the OSimage is selected based on a vendor identity for the mobile computingdevice.
 16. The system of claim 11, the mobile computing deviceconfiguration logic to further: configure the mobile computing device toconnect to a server including an OS update patch for the mobilecomputing device to download and install.
 17. The system of claim 11,wherein the short-range wireless communication interface comprises aNear Field Communication (NFC) interface.
 18. The system of claim 11,wherein the short-range wireless communication interface comprises aBluetooth communication interface.
 19. The system of claim 11, whereinthe mobile computing device to comprise at least one of a smartphone, atablet computing device, or a wearable computing device.
 20. At leastone non-transitory computer readable storage medium having instructionsstored thereon that, when executed on at least one machine, cause the atleast one machine to: wirelessly transmit power to a mobile computingdevice housed within a sealed product packaging to charge a batterypower supply of the mobile computing device; establish a short-rangewireless communication link with the mobile computing device housedwithin the sealed product packaging to install a firmware image on themobile computing device; use the short-range wireless communication linkto activate a wireless network interface of the mobile computing devicehoused within the sealed product packaging to connect to a boot serverincluding an operating system (OS) image for the mobile computing deviceto download and install, and configure the mobile computing device tolink the mobile computing device within the sealed product packagingwith a second mobile computing device using the wireless network, themobile computing device to obtain user data and user configurations fromthe second mobile computing device via the wireless network link tocustomize the mobile computing device according to user preferences. 21.The storage medium of claim 20, further comprising instructions that,when executed by the at least one machine, cause the machine to performoperations comprising: select one of a plurality of OS images for themobile computing device.
 22. The storage medium of claim 20, furthercomprising instructions that, when executed by the at least one machine,cause the machine to perform operations comprising connect to a serverincluding an OS update patch for the mobile computing device to downloadand install.